Blog

ColdBox Platform v3.6.0 Released!

Brad Wood February 26, 2013

Spread the word

Brad Wood

February 26, 2013

Spread the word


Share your thoughts

logoWe are proud to announce ColdBox Platform release version 3.6.0 and ColdBox DevBox 2.3. This is an important minor release that addresses many important issues, but also introduces some great enhancements. There are no compatibility updates needed and here are our "What's New" guideline:

The major push to concurrency in our ColdBox 4.0 roadmap has been sponsored by the great people at Guardly, who leverages the ColdBox Platform for their enterprise suite of applications.  In this release we introduce asynchronous event driven programming via Interceptors.

Release Notes

Bug

  • [COLDBOX-106] - Fix the unregistration of module configuration interceptors
  • [COLDBOX-108] - RequestContextDecorator call configure after populating rc since it is broken now by Tom Schoor (Tutuka)
  • [COLDBOX-110] - Added XSS escaping to debug panel when iterating over request collection dump
  • [COLDBOX-111] - When defaultEvent configuration was empty it was not defaulting to "main.index"
  • [COLDBOX-119] - Added XSS escaping to bug report
  • [COLDBOX-123] - Fix for implicit layout bugs when using interceptors and overriding layouts
  • [COLDBOX-125] - Size Validator did not account for only the minimum size and min and max validators where not being registered
  • [COLDBOX-127] - Railo incompatibilities with session wrapper for base orm services

Improvement

  • [COLDBOX-100] - buildLink uses ssl by default if you are already in ssl, basically it stays on the http protcol that you are on by default thanks to Markus Schneebeli
  • [COLDBOX-112] - Updated Attesoro tool to latest build for bundle 1.8.01
  • [COLDBOX-113] - Added a default layout "main.cfm" so it is inline with ColdBox LITE
  • [COLDBOX-116] - Update all Application Templates for consistency
  • [COLDBOX-118] - Added new cf10 "content" argument to Mail object for adding mail params
  • [COLDBOX-122] - New argument sendToHeader for html helper link and meta functions
  • [COLDBOX-124] - Add useSSL and useTLS in mailservice newmail() function from mail settings
  • [COLDBOX-126] - Added getMyPlugin to proxy calls

New Feature

  • [COLDBOX-98] - Asynchronous Interceptors
  • [COLDBOX-101] - Enhance i18n plugin to add getFWLocaleDisplay(), getFWCountry(), getFWCountryCode(), getFWISO3CountryCode, getFWLanguage, getFWLanguageCode,getFWISO3LanguageCode
  • [COLDBOX-115] - Enhance i18n plugin to enable getters and setters for internal properties
  • [COLDBOX-121] - Added utility function convertValueToJavaType() and convertIDValueToJavaType() to base orm services and virtual services

Thanks for always supporting us!

Resources:

Add Your Comment

(2)

Feb 27, 2013 15:27:19 UTC

by GApatriot

The link for the what's new is for 3.5.3 instead of 3.6.0. Proper link is:

<a href=http://wiki.coldbox.org/wiki/WhatsNew:3.6.0.cfm">http://wiki.coldbox.org/wiki/WhatsNew:3.6.0.cfm</a>

Feb 27, 2013 16:59:09 UTC

by Brad Wood

Thanks for the note. The link has been fixed!

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026